Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Status NOTE, drop p id="w3c-status" #203

Merged
merged 1 commit into from
Oct 18, 2024
Merged

Status NOTE, drop p id="w3c-status" #203

merged 1 commit into from
Oct 18, 2024

Conversation

tantek
Copy link
Member

@tantek tantek commented Oct 18, 2024 •
edited by pr-preview bot
Loading

w3.org/pubrules lies, there is absolutely already an id="w3c-status" element when you view source on the Bikeshed generated document, so drop the explicit p id="w3c-status" element. change the Status in the metadata to NOTE to see if that works to generate a Group Note since neither WG-NOTE and IG-NOTE are appropriate for this

💥 Error: 400 Bad Request 💥

PR Preview failed to build. (Last tried on Oct 18, 2024, 1:29 AM UTC).

More

PR Preview relies on a number of web services to run. There seems to be an issue with the following one:

🚨 CSS Spec Preprocessor - CSS Spec Preprocessor is the web service used to build Bikeshed specs.

🔗 [Related URL]([object Object])

Error running preprocessor, returned code: 2.
FATAL ERROR: PROGRAMMING ERROR: Group 'W3C/AB' has type 'none', but none of the W3C Statuses are associated with that type.
Your document appears to use tabs to indent, but line 205 starts with spaces.
Your document appears to use tabs to indent, but line 206 starts with spaces.
Your document appears to use tabs to indent, but line 207 starts with spaces.
Your document appears to use tabs to indent, but line 208 starts with spaces.
Your document appears to use tabs to indent, but line 210 starts with spaces.
Your document appears to use tabs to indent, but line 211 starts with spaces.
Your document appears to use tabs to indent, but line 212 starts with spaces.
Your document appears to use tabs to indent, but line 213 starts with spaces.
Your document appears to use tabs to indent, but line 215 starts with spaces.
Your document appears to use tabs to indent, but line 216 starts with spaces.
Your document appears to use tabs to indent, but line 218 starts with spaces.
Your document appears to use tabs to indent, but line 219 starts with spaces.
Your document appears to use tabs to indent, but line 220 starts with spaces.
Your document appears to use tabs to indent, but line 221 starts with spaces.
Your document appears to use tabs to indent, but line 222 starts with spaces.
Your document appears to use tabs to indent, but line 224 starts with spaces.
Your document appears to use tabs to indent, but line 225 starts with spaces.
Your document appears to use tabs to indent, but line 227 starts with spaces.
Your document appears to use tabs to indent, but line 228 starts with spaces.
 ✘  Did not generate, due to errors exceeding the allowed error level.

If you don't have enough information above to solve the error by yourself (or to understand to which web service the error is related to, if any), please file an issue.

@tantek
Status NOTE, drop p id="w3c-status"
da075bb 
w3.org/pubrules lies, there is absolutely already an id="w3c-status" element when you view source on the Bikeshed generated document, so drop the explicit p id="w3c-status" element.
change the Status in the metadata to NOTE to see if that works to generate a Group Note since neither WG-NOTE and IG-NOTE are appropriate for this
@tantek tantek merged commit 4e5df1e into main Oct 18, 2024
4 checks passed
@tantek tantek deleted the tantek-patch-4 branch October 18, 2024 01:30
@tantek tantek added the Project Vision Vision and Principles label Oct 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
Project Vision Vision and Principles
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@tantek